home *** CD-ROM | disk | FTP | other *** search
-
- OPUS
-
- (c) Copyright 1986, Wynn Wagner III, All Rights Reserved
-
-
-
-
-
-
-
-
- CHOICES
-
- 11 October 1986
-
-
-
-
-
-
-
-
-
-
- "In case of fire, yell FIRE!"
- --- The Management
-
-
-
-
-
- This pamphlet describes the menu files (or "priv files") used by Opus.
-
- Opus needs 5 menu files. Unlike Fido<tm>, Opus contains no built-in
- menus. If the files are not available, your Opus system will fail to
- operate correctly.
-
- Although Opus should operate correctly with most Fido<tm> menu files,
- it's better and safer to use the Opus files.
-
- Here is a list of the menu files. The Opus-only commands are listed
- in this chart ...
-
-
- | Menu file | Notes |
- |--------------+--------------------------------------------------|
- | MAINPRIV.BBS | The main menu |
- |--------------+--------------------------------------------------|
- | CHGPRIV.BBS | The change setup menu |
- | | * G)RAPHICS |
- | | * S)CREEN CLEAR |
- | | NOTE: N)ame is not currently supported |
- |--------------+--------------------------------------------------|
- | FILEPRIV.BBS | The file section menu |
- | | * C)ONTENTS |
- | | * H)URL |
- | | * O)RPHAN |
- | | |
- | | NOTE: four other commands are available |
- | | but don't appear on the menu: |
- | | |
- | | LV ... list verbose |
- | | SV ... scan verbose |
- | | L* ... list new |
- | | LV* ... list verbose new |
- |--------------+--------------------------------------------------|
- | MSGPRIV.BBS | The message section menu |
- | | NOTE: K)ILL is not supported on this |
- | | menu. It is included on the |
- | | read-messages menu |
- | | NOTE: S)TATS in Fido<tm> is called |
- | | S)CAN in Opus. |
- |--------------+--------------------------------------------------|
- | MAILPRIV.BBS | The network menu |
- |--------------+--------------------------------------------------|
- | READPRIV.BBS | The read-messages menu |
- | | * =)NON-STOP READ |
- | | NOTE: Message threads in this |
- | | release misbehave sometimes. We |
- | | suggest you set + and - to hidden. |
- +--------------+--------------------------------------------------+
-
-
-
-
- ADVANCED TOPICS
- ------------------------------------------------------------------------------
- You will find advanced customization features here. If you consider
- yourself a novice sysop, please put the rest of this pamphlet away until
- a later date. You can lead a meaningful life without going through any of
- this material. In fact, you could end up doing more damage than good
- unless you really know what you are doing.
-
-
-
-
-
- STRUCTURE
- ------------------------------------------------------------------------------
- There is no difference in the physical format of the files. Both systems
- use an array of records or structures. Here is the C-language definition
- of the menu structure:
-
- struct _cmd {
- char name[20];
- int priv;
- };
-
-
-
-
-
- FUNCTIONAL DIFFERENCES: COMMANDS
- ------------------------------------------------------------------------------
- Opus does not demand any particular character be used for the various menu
- selections. In other words, if you don't like "M)ain-menu" on a particular
- menu, there's nothing to stop you from using a message editor or a low level
- file editor (eg. Norton) to change the selection into "T)op".
-
- The POSITION of the menu selection is very important. In the above example,
- if "M)ain-menu" is, say, the third item in the menu file, you must make
- sure you put "T)op" in the third position.
-
- The command character must be an uppercase alpha character (ie A,B,C..Z).
- You should NEVER use a digit or punctuation.
-
- It is your responsibility to make sure you don't duplicate a character on
- the same menu. In other words, if you use "M" for two commands, the second
- command will be unavailable.
-
-
-
-
- FUNCTIONAL DIFFERENCES: DISPLAY
- ------------------------------------------------------------------------------
- Some system operators add spaces to the end of various menu commands using
- a low-level file editor. This is an attempt to force Fido<tm> to line up
- menus in columns.
-
- Such an effort is meaningless here. Opus always displays Novice menus
- in a columnar format. In fact, Opus will adjust the menu display to fit
- the caller's screen width.
-
-
-
-
-
- PROGRAMMER'S OPINION ON CUSTOMIZED MENUS
- ------------------------------------------------------------------------------
- One of the strongest points in favor of Fido<tm> is the similarity between
- systems. If you call any Fido<tm> BBS, then you know which characters
- do what actions.
-
- Opus gives its system operator an order of magnitude more power than does
- Fido<tm>. Along with this freedom to customize various features comes a
- great deal of responsibility.
-
- You have the ability to customize menus, but I personally think it's a
- very very very very bad idea to change everything just to be different.
-
- An example of a good place for customizing is the "E" command on the main
- menu. Some sysops want an "E)ditorial." Others want "E)xtra info." You
- might even want something like "W)ant ads". Those sorts of changes are
- wonderful and can had a personal touch to your system.
-
- Changing "R)ead messages" into "V)iew messages", on the other hand, is
- gratuitous modification. It can only confuse the users.
-
- So, while I feel that it's a good idea to give you lots of freedom and
- power over your system, I also feel that I need to ask that you not abuse
- that freedom and power.
-
-
- ###
-
-